1) CONCEP.TEX[CLS,LSP] and 2) CONCEP.18[CLS,LSP]	8-24-87 12:42	pages 1,1

**** File 1) CONCEP.TEX[CLS,LSP]/1P/601L
1)	name.  The {\bf defclass} and {\bf defstruct} constructs define both
1)	types and classes.  
1)	The name of every class is a valid type specifier.   In addition, every
**** File 2) CONCEP.18[CLS,LSP]/1P/601L
2)	name.  {\bf defclass} and {\bf defstruct} define both types and classes.  
2)	The name of every class is a valid type specifier.   In addition, every
***************


**** File 1) CONCEP.TEX[CLS,LSP]/1P/618L
1)	instance of a standard type class with {\bf make-instance} or to include
1)	a standard type class as a superclass of a class.
**** File 2) CONCEP.18[CLS,LSP]/1P/617L
2)	instance of a standard type class with {\bf make-instance} nor to include
2)	a standard type class as a superclass of a class.
***************


**** File 1) CONCEP.TEX[CLS,LSP]/1P/629L
1)	determined for each class.  This list orders the class and its superclasses
1)	from  most to least specific.  In some cases, {\it Common Lisp: The 
1)	Language\/} does not specify a subtype/supertype relationship for two 
1)	supertypes of a given type.   For example, {\bf null} is a subtype of
1)	both {\bf symbol} and {\bf list}, but {\it Common Lisp: The Language\/} 
1)	does not specify whether {\bf symbol} is more or less specific than {\bf
1)	list}.  The \CLOS\ specification defines those relationships for all
**** File 2) CONCEP.18[CLS,LSP]/1P/628L
2)	determined for each class, ordering the class and its superclasses from 
2)	most to least specific.  In some cases, {\it Common Lisp:  the 
2)	Language\/} does not specify a subtype/supertype relationship for two 
2)	supertypes of a given type.   For example, {\bf null} is a subtype of
2)	{\bf symbol} and {\bf list}, but {\it Common Lisp:  the Language\/} does
2)	not specify whether {\bf symbol} is more or less specific than {\bf
2)	list}.  The \CLOS\ specification defines those relationships for all
***************


**** File 1) CONCEP.TEX[CLS,LSP]/1P/639L
1)	\CLOS.  The superclasses of each standard type class are presented in
1)	order from most specific to most general.
1)	\boxfig
1)	{\dimen0=.75pc
1)	\tabskip \dimen0 plus .5 fil
1)	\halign to \hsize {#\hfil\tabskip \dimen0 plus 1fil&#\hfil\tabskip \dimen0 plus .5 fil&&#\hfil\cr  %was &&#
1)	\noalign{\vskip -9pt}
1)	\hfil\bf Standard Type Class&\hfil\bf Superclasses\span\omit\span\omit\cr
1)	\noalign{\vskip 2pt\hrule\vskip 2pt}
  1) CONCEP.TEX[CLS,LSP] and 2) CONCEP.18[CLS,LSP]	8-24-87 12:42	pages 1,1

1)	array&t\cr
1)	bit-vector&vector, array, sequence, t\cr
1)	character&t\cr
1)	complex&number, t\cr
1)	cons&list, sequence, t\cr
1)	float&number, t\cr
1)	integer&rational, number, t\cr
1)	list&sequence, t \cr
1)	null&list, symbol, sequence, t\cr
1)	number&t\cr
1)	ratio&rational, number, t\cr
1)	rational&number, t\cr
1)	sequence&t\cr
1)	string&vector, array, sequence, t\cr
1)	symbol&t\cr
1)	t\cr
1)	vector&array, sequence, t\cr
1)	\noalign{\vskip -9pt}
1)	}}
1)	\caption{}
1)	\endfig
1)	 
**** File 2) CONCEP.18[CLS,LSP]/1P/638L
2)	\CLOS\.  The superclasses of each standard type class are presented in
2)	order from most specific to most general: 
2)	    STANDARD TYPE CLASS		SUPERCLASSES 
2)	    array			t
2)	    bit-vector			vector, array, sequence, t
2)	    character			t
2)	    complex			number, t
2)	    cons			sequence, t
2)	    float			number, t
2)	    integer			rational, number, t
2)	    list			cons, sequence, t 
2)	    null			list, cons, symbol, sequence, t
2)	    number			t
2)	    ratio			rational, number, t
2)	    rational			number, t
2)	    sequence			t
2)	    string			vector, array, sequence, t
2)	    symbol			t
2)	    t
2)	    vector			array, sequence, t
2)	 
***************


**** File 1) CONCEP.TEX[CLS,LSP]/1P/675L
  1) CONCEP.TEX[CLS,LSP] and 2) CONCEP.18[CLS,LSP]	8-24-87 12:42	pages 1,1

1)	corresponding class.  Individual implementations can also add additional
1)	subclass relationships as long as they do not violate {\it Common Lisp:
**** File 2) CONCEP.18[CLS,LSP]/1P/665L
2)	corresponding class.  Also individual implementations can add additional
2)	subclass relationships as long as they do not violate {\it Common Lisp:
***************


**** File 1) CONCEP.TEX[CLS,LSP]/1P/688L
1)	%For a discussion on some of the design decisions underlying this aspect
1)	%of \CLOS\, see the section ``Design Theories of the Integration of Types
1)	%and Classes''.
1)	\endSection%{Integrating Types and Classes}
**** File 2) CONCEP.18[CLS,LSP]/1P/678L
2)	For a discussion on some of the design decisions underlying this aspect
2)	of \CLOS\, see the section ``Design Theories of the Integration of Types
2)	and Classes''.
2)	\endSection%{Integrating Types and Classes}
***************